-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(jdbc-sink): relax the check for UPDATE_DELETE op #17289
Conversation
cae66b8
to
4ae9444
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest LGTM.
Just curious that when will we miss the upsert delete?
@@ -185,6 +185,9 @@ impl<F: LogStoreFactory> SinkExecutor<F> { | |||
&& !self.sink_param.downstream_pk.is_empty(); | |||
// Don't compact chunk for blackhole sink for better benchmark performance. | |||
let compact_chunk = !self.sink.is_blackhole(); | |||
tracing::info!("Sink info: sink_id: {} actor_id: {}, need_advance_delete: {}, re_construct_with_sink_pk: {}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be tracing::info!(sink_id, actor_id, need_advanc_delete, re_construct_with_sink_pk, "sink info")
to avoid manually generating the format string.
Not sure why, more context here https://risingwave-labs.slack.com/archives/C06F37346CR/p1718669258478389 |
I forgot to add the cherry-pick action for v1.10, I will relabel to trigger the action after #17301 |
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
It should be safe to ignore the
U-
op in jdbc sink, since we useUPSERT
to deliver events into downstream database which can resolve the inconsistent events.related: #14031
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.